Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/app/components/demos/mesh-demo.tsx`:
- Around line 143-144: The token limit check in the loop uses a greater-than
comparison operator which allows the tokens array to exceed the intended maximum
by one element. Change the condition from `>` to `>=` in the comparison
`sim.tokens.length > MAX_TOKENS` to ensure the loop breaks immediately when the
token count reaches MAX_TOKENS rather than allowing it to go one beyond the
limit.
- Line 123: The MeshDemo component function signature does not accept the theme
prop that is being passed to it from DemoModal. Update the function signature of
MeshDemo to accept a destructured theme prop with the DemoProps type annotation,
changing from a function with no parameters to one that destructures the theme
property from the DemoProps interface. This will ensure the component properly
receives and can use the theme value passed by its parent.

In `@docs/app/components/demos/recovery-demo.tsx`:
- Around line 174-185: When reduced-motion mode becomes true during playback,
the RAF loop stops executing (due to the `playing && !reduced` condition in
useRafLoop at line 174), but the `playing` state remains true, leaving the UI in
a stale "Pause" state. Fix this by ensuring that when `reduced` is true in the
`startPlay` callback, you also call `setPlaying(false)` to keep the `playing`
state synchronized with the actual playback state, so the UI control reflects
the frozen timeline correctly.

In `@docs/app/components/demos/registry.ts`:
- Around line 22-24: The demoComponent function uses unchecked property access
on DEMO_COMPONENTS which can return inherited prototype properties for strings
like __proto__ instead of only own properties. Guard the lookup in demoComponent
to verify the id exists as an own property of DEMO_COMPONENTS using
Object.hasOwn() or Object.prototype.hasOwnProperty.call() before returning the
value, otherwise return undefined to maintain the documented behavior of
returning undefined for unknown ids.

In `@docs/app/components/demos/saga-demo.tsx`:
- Line 126: The SagaDemo function signature does not accept the DemoProps
parameter, which causes a type mismatch with the registry contract that expects
ComponentType<DemoProps>. Modify the SagaDemo function to accept DemoProps as a
parameter in its signature to maintain type consistency with the registry, even
if the props are not immediately used within the component.

In `@docs/app/components/demos/workflow-demo.tsx`:
- Line 203: The WorkflowDemo component does not accept the DemoProps parameter
in its function signature, which violates the ComponentType<DemoProps> contract
defined in the registry. Update the WorkflowDemo function signature to accept
props of type DemoProps as a parameter (similar to how ScalingDemo implements
it). This ensures the component matches the registry's type expectations and
properly receives the theme prop passed by DemoModal at line 185, maintaining
consistency with the type system even if the component currently relies on CSS
variables for theming.

In `@docs/app/components/demos/worksteal-demo.tsx`:
- Around line 316-317: The simulation uses wall-clock timestamps from
performance.now() to track job/token deadlines, but the pause mechanism only
stops RAF scheduling, allowing real time to advance during the pause. When
resumed after a long pause, deadlines calculated relative to the old timestamps
become stale and expire immediately. Fix this by tracking cumulative pause
duration and adjusting all timestamp-based deadline calculations throughout the
simulation. Specifically, capture the pause start time when paused becomes true
and accumulate the elapsed pause duration when paused becomes false, then offset
all performance.now() calls used in deadline calculations (such as the rs.busy
assignment and similar deadline-setting code in other locations marked in the
"Also applies to" note) by subtracting the total accumulated pause time so that
paused duration does not count toward expiration.
- Around line 465-490: The Pause/Resume button toggle does not expose its
current state to assistive technology. Add the aria-pressed attribute to the
button element (the one with className "ctl" that has onClick={() =>
setPaused((p) => !p)}) and set it equal to the paused state variable to properly
communicate the button's toggled state to screen readers and other accessibility
tools.

---

Outside diff comments:
In `@docs/app/components/landing/demo-modal.tsx`:
- Around line 89-103: The focus-trap selector in the useEffect hook is
incomplete and does not include native form controls. Expand the querySelector
selector string used in the querySelectorAll call (currently selecting only a,
button, iframe, and tabindex elements) to also include input, select, and
textarea elements so that all focusable form controls are properly trapped
within the dialog when Tab focus navigation occurs.

---

Nitpick comments:
In `@docs/app/components/demos/ratelimit-demo.tsx`:
- Line 94: The RateLimitDemo component function signature does not accept the
DemoProps parameter, but the DemoModal integration passes a theme prop to all
demo components. Update the RateLimitDemo function declaration to accept the
DemoProps interface as a parameter. If DemoProps is not already exported from
types, import it first, then add the parameter to match the registry contract
that DemoModal expects when it renders the component with the theme prop.

In `@docs/app/components/demos/scaling-demo.tsx`:
- Around line 292-296: The loop callback uses a fixed timestep instead of
frame-rate-independent timing, which causes inconsistent simulation speeds on
different display refresh rates. Modify the loop callback to use the now
parameter provided by useRafLoop to calculate the actual delta time elapsed
since the last frame, then pass this delta time to stepSim instead of the
hardcoded 0.04s value. Track the previous frame timestamp to compute the elapsed
time between frames and ensure the simulation runs at consistent speed
regardless of device refresh rate.

In `@docs/app/components/demos/workflow-demo.tsx`:
- Around line 222-249: The spawnDot callback spawns requestAnimationFrame
animations via the move function that can continue executing after component
unmount, wasting resources on detached elements. Create a Set-based ref to track
active animation frame IDs, store each requestAnimationFrame(move) return value
in this tracking Set, remove completed animation frame IDs when animations
finish (when p >= 1), and add a useEffect cleanup function that cancels all
remaining tracked animation frames when the component unmounts using
cancelAnimationFrame.